Enabling interface aggregation of mobile broadband network interfaces

ABSTRACT

A network traffic associated with a communication request within a computing device can be identified. The device can comprise of a first and second communication stack which can addresses a first and a second network interface within the computing device. The first network interface can be associated with a mobile broadband network and the second network interface can be associated with a computing network. A first and second portion of the network traffic associated with the communication request can be programmatically determined to be conveyed to the first and second network interfaces. The first and second portions of network traffic can be conveyed simultaneously to the mobile broadband network associated with the first network interface and the computing network associated with the second network interface.

BACKGROUND

The present disclosure relates to the field of network communicationsand, more particularly, to enabling interface aggregation of mobilebroadband network interfaces.

Mobile computing devices (e.g., mobile phones) are becoming increasinglyversatile and feature rich. Many of these mobile computing devices areequipped with multiple forms of network access which can include mobilebroadband (e.g., 3G), and wireless broadband (e.g., Wi-MAX). Thesewireless broadband technologies (e.g., Wi-Fi, LTE) traditionally provideusers with Internet access. Frequently, only a portion of the totalbandwidth of a mobile broadband connection can be available due toconnectivity issues such as limited coverage areas and radio frequencyinterference. As such, users can experience long wait times wheninteracting with Internet resources due to high latency as a result ofthese connectivity issues. For instance, content dense Web sites can beresult in significant delays due to high latency on mobile broadbandnetworks.

Currently, users must choose which mobile broadband technology ispreferred (e.g., Wi-Fi) and utilize that mobile broadband service only.In many instances, applications executing on mobile phones are utilizingincreasing amounts of bandwidth of mobile broadband connections.Frequently, the broadband connection can be outpaced by the applicationexecuting on the mobile device. That is, it is not uncommon for abroadband connection can become saturated by one network-basedapplication executing on a mobile device, leaving the user unable toutilize other network-centric applications until the broadbandconnection is available. This negatively affects user experience sincethe mobile device can permit the use of multiple network-basedapplications simultaneously.

In many situations, several methods of connectivity can be available tousers such as access to multiple hotspots (e.g., wireless accesspoints), wired connectivity, and mobile broadband access. For example,many coffee houses (e.g., STARBUCKS) offer Wi-Fi hotspots whichcustomers can take advantage of during their patronage by connectingtheir mobile devices to the provided Wi-Fi network. Consequently,available broadband connections (e.g., 3G mobile broadband) can gounused. Consequently, the user experience is becoming increasinglydegraded by lack of connectivity options and bandwidth availability.

SUMMARY

A network traffic associated with a communication request within acomputing device can be identified. The device can be comprise of afirst and second communication stack which can address a first and asecond network interface within the computing device. The first networkinterface can be associated with a mobile broadband network and thesecond network interface can be associated with a computing network. Afirst and second portion of the network traffic associated with thecommunication request can be programmatically determined to be conveyedto the first and second network interfaces. The first and secondportions of network traffic can be conveyed simultaneously to the mobilebroadband network associated with the first network interface and thecomputing network associated with the second network interface.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1A is a schematic diagram illustrating a scenario for enablinginterface aggregation of mobile broadband network interfaces inaccordance with an embodiment of the inventive arrangements disclosedherein.

FIG. 1B is a schematic diagram illustrating a scenario for enablinginterface aggregation of mobile broadband network interfaces inaccordance with an embodiment of the inventive arrangements disclosedherein.

FIG. 2 is a schematic diagram illustrating a model of a communicationstack for enabling interface aggregation of mobile broadband networkinterfaces in accordance with an embodiment of the inventivearrangements disclosed herein.

FIG. 3 is a schematic diagram illustrating a system for enablinginterface aggregation of mobile broadband network interfaces inaccordance with an embodiment of the inventive arrangements disclosedherein.

FIG. 4 is a schematic diagram illustrating a system for enablinginterface aggregation of mobile broadband network interfaces inaccordance with an embodiment of the inventive arrangements disclosedherein.

DETAILED DESCRIPTION

The present disclosure is a solution for enabling interface aggregationof mobile broadband network interfaces. In the solution, a mobilebroadband network interface can be combined with another networkinterface to obtain improved bandwidth. The mobile broadband networkinterface can be an interface associated with a mobile phone networksuch as a Long Term Evolution (LTE) network. The combined networkinterfaces can be addressed as a logical interface via a network fusioncommunication stack. That is, the heterogeneous network interfaces canbe utilized as a single network interface to enhance network speeds on acomputing device.

As will be appreciated by one skilled in the art, the present disclosuremay be embodied as a system, method or computer program product.Accordingly, the present disclosure may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present disclosure may take the form of a computer program productembodied in any tangible medium of expression having computer usableprogram code embodied in the medium.

Any combination of one or more computer usable or computer readablemedium(s) may be utilized. The computer-usable or computer-readablemedium may be, for example but not limited to, an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system, apparatus,device, or propagation medium. More specific examples (a non-exhaustivelist) of the computer-readable medium would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CDROM), an optical storage device, a transmission media such as thosesupporting the Internet or an intranet, or a magnetic storage device.Note that the computer-usable or computer-readable medium could even bepaper or another suitable medium upon which the program is printed, asthe program can be electronically captured, for instance, via opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory. In the context of this document, a computer-usableor computer-readable medium may be any medium that can contain, store,communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.The computer-usable medium may include a propagated data signal with thecomputer-usable program code embodied therewith, either in baseband oras part of a carrier wave. The computer usable program code may betransmitted using any appropriate medium, including but not limited towireless, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the presentdisclosure may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava, Smalltalk, C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The program code may execute entirely on the user's computer,partly on the user's computer, as a stand-alone software package, partlyon the user's computer and partly on a remote computer or entirely onthe remote computer or server. In the latter scenario, the remotecomputer may be connected to the user's computer through any type ofnetwork, including a local area network (LAN) or a wide area network(WAN), or the connection may be made to an external computer (forexample, through the Internet using an Internet Service Provider).

The present disclosure is described below with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products according to embodiments of the disclosure. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce amachine, such that the instructions, which execute via the processor ofthe computer or other programmable data processing apparatus, createmeans for implementing the functions/acts specified in the flowchartand/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide processes for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

FIG. 1A and FIG. 1B is a schematic diagram 100A, 100B illustrating ascenario 105, 150 for enabling interface aggregation of mobile broadbandnetwork interfaces in accordance with an embodiment of the inventivearrangements disclosed herein. In the scenario 105, 150, network fusionlayer 120, 170 can enable multiple mobile broadband interfacesassociated with network interfaces 124-128, 174-178 to be utilizedsimultaneously. That is, network fusion layer 120, 170 can permitseamless aggregation of broadband interfaces into a logical networkinterface which can be protocol independent. Consequently, mobile device110, 160 network traffic can be transparently and easily communicatedacross any combination of the aggregated interfaces 124-128, 174-178enabling maximum bandwidth utilization. For instance, application 112can utilize a third generation (3G) interface 124 and Wi-Fi interface128 simultaneously to communicate with application server 140.

In the scenario 105, 150, mobile device 110, 160 can comprise of networkfusion layer 120, 170. Network fusion layer 120, 170 can replace and/orsupplement a traditional communication stack within device 110, 160. Inone instance, network fusion layer 120, 170 can reside within acommunication stack between the application layer and the data linklayer conforming to the Open Systems Interconnect (OSI) model. Thus, thenetwork fusion layer is an additionally layer of abstraction, whichinterfaces with subordinate and superior layers. Consequently, existingsoftware/hardware operating at any of the traditional layers ofabstraction (of the OSI) model will be able to seemly interoperate withthe network fusion layer. In one embodiment, optimizations can beimplemented so that the network fusion layer results in some changes tothe data link layer and/or application layer instead of beingimplemented as a separate, discrete layer of abstraction.

Mobile device 110, 160 can be hardware/software computing device capableof interfacing with at least two or more broadband networks. Mobiledevice 110, 160 can include, but is not limited to, mobile phone,laptop, netbook, mobile computing device (e.g., tablet), portablemultimedia player, portable digital assistant, and the like. Mobiledevice 110, 160 can include two or more network interfaces 124-126,174-178 able to communicate with mobile broadband networks. Mobiledevice 110, 160 can execute one or more applications 112-116, 162.

Applications 112-116, 162 can include, but are not limited to, firmwareapplications, software applications, and the like. Applications 112-116,162 can communicate with application servers 140-144, 190 which cangenerate network traffic (e.g., dashed lines). For example, applications112-116 can be mobile applications such as a Web browser, email client,and calendar application. Network traffic can be conveyed over networkinterfaces 124-128, 174-178.

Network interfaces 124-128, 174-178 can be a hardware/software modemsenabling connectivity to broadband networks. Network interfaces 124-128,174-178 can include, but is not limited to, cellular modems, wirelessmodems, and the like. Interfaces 124-128, 174-178 can be locatedinternally and/or externally to mobile device 110, 160. For instance,network interface 124 can be a Universal Mobile TelecommunicationsSystem portable computer (PC) card.

Networks 130-134, 180-184 associated with interfaces 124-128, 174-178can be communication networks enabling access to local and/or remoteresources. For example, networks can enable Internet access for mobiledevices 110, 160. Networks 130-134, 180-184 can include, but are notlimited to mobile phone networks, cellular networks, telephony networks,wireless wide area networks (WAN), wired networks, and the like.Interfaces 124-128, 174-178 can be associated with networks 130-134,180-184 which can permit communicate with mobile device 110, 160applications 112-116, 162 in one or more traditional fashions.

Fusion layer 120, 170 can facilitate communication between applications112-116, 162 and data link layer 122, 172 by providing protocoltranslation when necessary. Layer 120, 170 can provide traditionaland/or proprietary communication functionality for the aggregatedinterfaces 130-134, 180-184. That is, applications 112-116, 162 canrequire no modification to utilize the aggregated bandwidth provided bylayer 120, 170. Layer 120, 170 can provide communication dataformatting, session control, transport management, network routing, andthe like.

It should be appreciated conventional interface aggregation managementfunctions can be present within layer 120, 170. Interface aggregationmanagement functions can include, but is not limited to, load balancing,interface discovery, interface configuration, fault tolerance, frameordering, frame synchronization, security, and the like. In oneinstance, layer 120, 170 can be configured to utilize one or morespecific interfaces based on network traffic content type, availablebandwidth, application type, and the like. For example, low bandwidthconnections can be preferred when application network traffic is nottime critical enabling higher bandwidth connections to be free for useby real-time applications. It should be noted, layer 120, 170 can beconfigured to permit arbitrarily granular control over network trafficwithin mobile device 110, 160. Control can include, application sessioncontrol, protocol control, frame control, packet control, and the like.For instance, individual packets can be routed over multiple interfaces124-128 (e.g., data stripping).

In scenario 105, applications 112-116 can communicate individually withapplication servers 140-144. Network fusion layer 120 can independentlymanage the communication between each application 112-116, data linklayer 122, and application server 140-144. That is, each application112-116 can have a dedicated interface 124-128 for communicating withapplication server 140-144. In another embodiment, layer 120 candynamically manage application traffic based on one or moreprioritization criteria. Prioritization criteria can include applicationprioritization, network prioritization, interface prioritization, andthe like.

In scenario 150, application 162 can communicate with application server190 utilizing interfaces 174-178. Layer 170 can perform multi-linkrouting for application 162 network traffic across interfaces 174-178based on one or more conditions. Conditions can include, but is notlimited to, heuristically determined settings, user-establishedconfiguration parameters, and the like. For instance, a portion of a Webpage request can be communicated over each interface: JAVASCRIPT contentcan be conveyed over interface 174, Hypertext Markup Language (HTML)content can be communicated via interface 176, and images can beconveyed using interface 178. In this way, each interface can beoptimally utilized based on network bandwidth, latency, and the like.

As used herein, mobile broadband networks can include, but is notlimited to 3G mobile phone networks, 4G mobile phone networks, Long TermEvolution (LTE) networks, Global System for Mobile Communications (GSM)networks, Code Division Multiple Access (CDMA) network, Wi-Fi network,Worldwide Interoperability for Microwave Access (Wi-MAX) network, wirednetworks, and the like.

Drawings presented herein are for illustrative purposes only and shouldnot be construed to limit the disclosure in any regard. It should beappreciated networks associated with scenario 105, 150 can includecircuit switched networks, packet switched networks, and the like. Itshould be appreciated, networks 180-184 can support multi-link routingpermitting distributed traffic to be conveyed between mobile device 160and application server 190. That is, scenario 150 demonstrates a systemin which the fusion layer exists within a mobile device and anotherend-point computing device (e.g., gateway router) permitting thescenarios to occur.

FIG. 2 is a schematic diagram illustrating a model 200 of acommunication stack for enabling interface aggregation of mobilebroadband network interfaces in accordance with an embodiment of theinventive arrangements disclosed herein. Model 200 can be present in thecontext of scenarios 105, 150, and system 300, 400. Model 200 caninclude a group of network communication layers conforming to an OpenSystems Interconnect (OSI) model.

Model 200 can be two or more hardware/software communication stacksassociated with a computing device (e.g., router). Model 200 cancomprise of wireless broadband communication stack 220 and genericcommunication stack 230. Network fusion layer 250 can include portions(e.g., layers) of communication stacks including, but not limited to,wireless broadband communication stack 220, generic communication stack230, wired communication stack, and the like.

Communication stack 220, 230 can be a hardware/software communicationstack associated with a wireless broadband technology and/or wiredbroadband technology. It should be appreciated stacks 220, 230 caninclude, but is not limited to layers 221-227, 231-237. Communicationstacks 220, 230 can include, but are not limited to, 3G/4G compliantstack, 802.3, 802.11, 802.15, 802.16, and the like. For instance, stack220 can be a Wireless Application Protocol stack and stack 230 can be aTransport Control Protocol/Internet Protocol (TCP/IP) communicationstack. That is, the disclosure can enable management of differingprotocol stacks having heterogeneous layer formations.

In model 200, layers 222-225, 232-235 can exist within a network fusionlayer 250. In one instance, network fusion layer 250 can be a wrapperimplementation. In the instance, layer 250 can be a wrapper softwaredriver able to manage traditional and/or proprietary layers 222-225,232-235 within stacks 220, 230 uniformly. For example, layer 250 can bea third party software driver enabling control over operating systemlevel communication stacks 220, 230. In another instance, layers222-225, 232-235 can be specialized network fusion layers able to besynchronized during interface aggregation.

In one instance, network fusion layer 250 can be one or moremicro-layers within a communication stack. In the instance, layer 250can be a combination of multiple micro-layers that control the mediationbetween different technology protocols providing bandwidth improvement,high availability, and security.

It should be appreciated model 200 represents one implementation of thedisclosure and should not be construed to limit the disclosure in anyregard. Layers within model 200 can be omitted and/or combined based oncommunication stack implementation (e.g., TCP/IP). In one embodiment,model 200 can be a portion of a networking application programminginterface permitting interface aggregation to be performed trivially(e.g., via function calls).

FIG. 3 is a schematic diagram illustrating a system 300 for enablinginterface aggregation of mobile broadband network interfaces inaccordance with an embodiment of the inventive arrangements disclosedherein. System 300 can be present in the context of scenario 105, 150,model 200, 400. In system 300, a computing device 310 can utilize fusionengine 340 to achieve broadband interface aggregation betweenheterogeneous broadband interfaces. System 300 can enable broadbandinterface aggregation within any network configuration including, butnot limited to, client-server, peer-to-peer, and the like.

Computing device 310 can be a hardware/software computing entity able toexecute fusion engine 340, operating system 332, and/or applications370. Computing device 310 can comprise of hardware 320 and software 330.Device 310 can be a mobile computing device, a router, network gatewaydevice, and the like. For instance, device 310 can be a WirelessApplication Protocol gateway configured to support interfaceaggregation.

Fusion engine 340 can be a hardware/software component enablingbroadband interface aggregation (e.g., aggregate interface 329). Engine340 can comprise of, but is not limited to, interface manager 350, datamanager 352, session handler 354, flow controller 356, routing engine358, and the like. In one instance, engine 340 can be a component of anoperating system 332. For example, engine 340 can be a operating systemcommunication driver. It should be appreciated, engine 340 enablesapplications 370 to utilize any interface available without requiringthe application 370 to perform any specialized communication. Forinstance, a Wireless Application Protocol (WAP) enabled application canutilize a Wi-Fi interface which can conform to Transport ControlProtocol/Internet Protocol.

Interface manager 350 can be a hardware/software component for managinginterface 329. Manager 350 can perform interface 329 changes including,but not limited to, interface activation, interface deactivation,interface configuration, and the like. Manager 350 can interact withengine 340 components to permit persistent interface aggregation. In oneembodiment, manager 350 can permit to interface customization byutilizing location profiles (e.g., rules 360). For example, manager 350can aggregate Ethernet and WiFi interfaces when a user is in theiroffice and a 3G and Wi-MAX interface when the user is away from theiroffice.

Data manager 352 can be a hardware/software component for organizingnetwork traffic data associated with interface 329. Manager 352functionality can include, but is not limited to formatting conversion,data structure management, serialization, encryption, and the like. Forexample, manager 352 can convert network payload data in real-time fromWireless Markup Language to an Extensible Markup Language (XML) format.In one embodiment, manager 352 can be used to encrypt and/or decryptnetwork traffic data from protocols associated with the aggregatedinterfaces. That is, manager 352 can enable any application 370 toutilize any interface within aggregate interface 329 transparently,regardless of encryption schemes and/or security protocols associatedwith the interface.

Session handler 354 can be a hardware/software component forestablishing and maintaining a session between application 370 and/orapplication 370 services. Handler 354 can provide, but is not limitedto, session authentication, synchronization, session check-pointing, andthe like. Handler 354 can be customized to enable session tracking forthe aggregate interface 329, each interface within aggregate interface329, and the like. Handler 354 can permit request/response transmissionsto occur over any interface 329. For example, a request can be conveyedover a 3G interface and the corresponding response can be received via aWorldwide Interoperability for Microwave Access (WiMAX) interface.

Flow controller 356 can be a hardware/software component forsynchronizing network traffic flow between application 370 and remoteresources over aggregate interface 329. Controller 356 functionality caninclude, but is not limited to, flow control, reliability, ordering, andthe like. Flow controller 356 can utilize traditional and/or proprietarychecksums to enable data integrity to be maintained. In one instance,controller 356 can utilize volatile memory 324 as a buffer during dataordering and/or flow control operations. Controller 356 protocols caninclude, but is not limited to Transport Control Protocol (TCP), UserDatagram Protocol (UDP), Datagram Congestion Control Protocol (DCCP) andthe Stream Control Transmission Protocol (SCTP), and the like.

Routing engine 358 can be a hardware/software entity for routing networktraffic data associated with application 370. Engine 358 can performconnectionless communication, connection-oriented communication, hostaddressing, message forwarding, and the like. Engine 358 can permitmulti-link routing for interface 329 which can include the routing ofnetwork traffic associated with local network addresses, public networkaddresses, and the like.

Rules 360 can be one or more policies for configuring the behavior offusion engine 340. Rules 360 can include application client interfacerules, network interface discovery rules, data splitting rules, datamerging rules, and the like. Rules 360 can be used to accommodatedifferent protocol stacks including traditional and/or proprietarycommunication stacks. In one instance, rules 360 can be established foreach interface, protocol, source, destination, and the like.

Application 370 can be a executable code able to communicate with anapplication server. Application 370 can be, but is not limited to, amobile application (e.g., client-side), server application, applicationsuite, enterprise software, and the like. Application 370 can interactwith aggregate interface 329 in a traditional manner via fusion engine340. It should be appreciated application 370 can reside external todevice 310 (e.g., Web service) based on device 310 embodiment, (e.g.,network router).

Drawings presented herein are for illustrative purposes only and shouldnot be construed to limit the disclosure any regard. System 300 can be astand-alone computing device, network computing device, distributedcomputing device, and the like. Hardware 320 can be physical computingcomponents permitting installation and execution of software 330.Hardware 320 can include, but is not limited to, processor 322, volatilememory 324, non-volatile memory 326, bus 328, and the like. Operatingsystem 330 can include, software, firmware, and the like.

FIG. 4 is a schematic diagram illustrating a system 400 for enablinginterface aggregation of mobile broadband network interfaces inaccordance with an embodiment of inventive arrangements disclosedherein. System 400 exemplifies one embodiment of a network fusionframework 410. Framework 410 can comprise of, but is not limited to,components 412, states 420, rules 430, and the like. System 400 can be aportion of a network management tool within a computing device (e.g.,laptop connection manager). For example, system 400 can be configuredvia an IBM THINKVANTAGE ACCESS CONNECTIONS software utility.

In one embodiment, rules 430 can permit customization for multipleprotocols, environments, and the like. In the embodiment, rules 430 canpermit configuration of individual components 412. It should beappreciated, components 412 can provide self-testing functionality,operational statistics, state information and the like.

The flowchart and block diagrams in the FIGS. 1-4 illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is:
 1. A computer-implemented method within a computerhardware system implementing an application layer and a data link layer,comprising: identifying, using a network fusion layer disposed betweenthe application layer and the data link layer, a first portion ofnetwork traffic from the application layer; identifying, using thenetwork fusion layer, a second portion of the network traffic from theapplication layer; routing, using the network fusion layer, the firstportion to a first network interface associated with a computingnetwork; and routing, using the network fusion layer, the second portionto a second network interface associated with a mobile phone network,wherein the identifying and the routing of the first and second portionsoccurs simultaneously, and wherein the network fusion layer includes: adata composer configured to assemble and disassemble a communicationrequest associated with the network traffic; a session handlerconfigured to establish a communication session between a source entityand at least one destination entity associated with the network traffic;a flow controller configured to moderate transmission speed of thenetwork traffic transmitted over a plurality of network links.
 2. Themethod of claim 1, wherein the first network interface is dedicated to afirst application in the application layer, and the second networkinterface is dedicated to a second application in the application layer.3. The method of claim 1, wherein the network fusion layer dynamicallymanages the network traffic based upon prioritization criteria.
 4. Themethod of claim 1, wherein the first and second network interfacereceive network traffic from a first application in the applicationlayer, the first network interface is dedicated to a predefined firstportion of the network traffic from the first application; the secondnetwork interface is dedicated to a predefined second portion of networktraffic from the first application.
 5. The method of claim 1, furthercomprising: identifying a state change of one of the first and secondnetwork interfaces; and automatically deactivating, upon the statechange being the one of the first and second network interfaces becomingunresponsive, the one of the first and second network interfaces.
 6. Themethod of claim 1, further comprising: receiving a communication requestwith a network access protocol destined to an interface having adifferent network access protocol; translating, using, the networkfusion layer, the communication request into the different networkaccess protocol; and conveying the communication request over theinterface via the different network access protocol.
 7. The method ofclaim 1, wherein the network fusion layer includes: a network interfacemanager configured to manage a plurality of the network interfacesassociated with the plurality of network links; and a routing engineconfigured to convey at least a portion of the communication request tothe source entity and the at least one destination entity utilizing theplurality of network links.
 8. A computer hardware system implementingan application layer and a data link layer, comprising: a hardwareprocessor configured to initiate the following executable operations:identifying, using a network fusion layer disposed between theapplication layer and the data link layer, a first portion of networktraffic from the application layer; identifying, using the networkfusion layer, a second portion of the network traffic from theapplication layer; routing, using the network fusion layer, the firstportion to a first network interface associated with a computingnetwork; and routing, using the network fusion layer, the second portionto a second network interface associated with a mobile phone network,wherein the identifying and the routing of the first and second portionsoccurs simultaneously, and wherein the network fusion layer includes: adata composer configured to assemble and disassemble a communicationrequest associated with the network traffic; a session handlerconfigured to establish a communication session between a source entityand at least one destination entity associated with the network traffic;a flow controller configured to moderate transmission speed of thenetwork traffic transmitted over a plurality of network links.
 9. Thesystem of claim 8, wherein the first network interface is dedicated to afirst application in the application layer, and the second networkinterface is dedicated to a second application in the application layer.10. The system of claim 8, wherein the network fusion layer dynamicallymanages the network traffic based upon prioritization criteria.
 11. Thesystem of claim 8, wherein the first and second network interfacereceive network traffic from a first application in the applicationlayer, the first network interface is dedicated to a predefined firstportion of the network traffic from the first application; the secondnetwork interface is dedicated to a predefined second portion of networktraffic from the first application.
 12. The system of claim 8, whereinthe hardware processor configured to initiate the following furtherexecutable operations: identifying a state change of one of the firstand second network interfaces; and automatically deactivating, upon thestate change being the one of the first and second network interfacesbecoming unresponsive, the one of the first and second networkinterfaces.
 13. The system of claim 8, wherein the hardware processorconfigured to initiate the following further executable operations:receiving a communication request with a network access protocoldestined to an interface having a different network access protocol;translating, using, the network fusion layer, the communication requestinto the different network access protocol; and conveying thecommunication request over the interface via the different networkaccess protocol.
 14. The system of claim 8, wherein the network fusionlayer includes: a network interface manager configured to manage aplurality of the network interfaces associated with the plurality ofnetwork links; and a routing engine configured to convey at least aportion of the communication request to the source entity and the atleast one destination entity utilizing the plurality of network links.15. A computer program product, comprising: a hardware storage devicehaving stored therein computer usable program code, the computer usableprogram code, which when executed by a computer hardware systemimplementing an application layer and a data link layer, causes thecomputer hardware system to perform: identifying, using a network fusionlayer disposed between the application layer and the data link layer, afirst portion of network traffic from the application layer;identifying, using the network fusion layer, a second portion of thenetwork traffic from the application layer; routing, using the networkfusion layer, the first portion to a first network interface associatedwith a computing network; and routing, using the network fusion layer,the second portion to a second network interface associated with amobile phone network, wherein the identifying and the routing of thefirst and second portions occurs simultaneously, and wherein the networkfusion layer includes: a data composer configured to assemble anddisassemble a communication request associated with the network traffic;a session handler configured to establish a communication sessionbetween a source entity and at least one destination entity associatedwith the network traffic; a flow controller configured to moderatetransmission speed of the network traffic transmitted over a pluralityof network links.
 16. The computer program product of claim 15, whereinthe first network interface is dedicated to a first application in theapplication layer, and the second network interface is dedicated to asecond application in the application layer.
 17. The computer programproduct of claim 15, wherein the network fusion layer dynamicallymanages the network traffic based upon prioritization criteria.
 18. Thecomputer program product of claim 15, wherein the first and secondnetwork interface receive network traffic from a first application inthe application layer, the first network interface is dedicated to apredefined first portion of the network traffic from the firstapplication; the second network interface is dedicated to a predefinedsecond portion of network traffic from the first application.
 19. Thecomputer program product of claim 15, wherein the computer usableprogram code further causes the computer hardware system to perform:identifying a state change of one of the first and second networkinterfaces; and automatically deactivating, upon the state change beingthe one of the first and second network interfaces becomingunresponsive, the one of the first and second network interfaces. 20.The computer program product of claim 15, wherein the computer usableprogram code further causes the computer hardware system to perform:receiving a communication request with a network access protocoldestined to an interface having a different network access protocol;translating, using, the network fusion layer, the communication requestinto the different network access protocol; and conveying thecommunication request over the interface via the different networkaccess protocol.